Method and system for sending and receiving data

ABSTRACT

A method and system for sending and receiving data, for use in solving the problem that an RLC layer may process a data packet in a whole only when a transmission time arrives, which renders a long processing time in the entire process. In embodiments of the present invention, received PDCP PDUs are combined into RLC PDUs and are allocated with corresponding RLC SNs, wherein each RLC PDU corresponds to an RLC SN, and each RLC PDU comprises at least one PDCP PDU; data corresponding to scheduling resources is generated according to the generated RLC PDUs; the data corresponding to the scheduling resources is combined into an MAC PDU for data receiving. The solution in the embodiments of the present invention may shorten the length of time in layer-2 data packet processing.

This application is a U.S. National Stage of International ApplicationNo. PCT/CN2017/105729, filed on Oct. 11, 2017, designating the UnitedStates, and claiming the benefit of Chinese Patent Application No.201610959950.6, filed with the Chinese Patent Office on Nov. 3, 2016,and entitled “A method and system for transmitting data, and a methodand system for receiving data”, which is hereby incorporated byreference in its entirety.

FIELD

The present application relates to the field of wireless communications,and particularly to a method and system for transmitting data, and amethod and system for receiving data.

BACKGROUND

Data are generally transmitted between a user Equipment (UE) and anevolved Node B (eNB) through a Packet Data Convergence Protocol (PDCP)layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC)layer, and a Physical (PHY) layer, each of which processes the datadifferently. The PDCP layer generally performs security operations, andheader compression and decompression, e.g., encryption and integrityprotection, Robust Header Compression (ROHC) and decompression, etc.;the RLC layer generally segments the data, concatenates data segments,delivers the data segments in sequence, guarantees transmission ofAutomatic Repeat reQuest (ARQ) data, etc.; the processing modulegenerally schedules the data, concatenates different logical channels,performs Hybrid Automatic Repeat reQuest (HARQ) operations, etc.; andthe PHY layer generally packages a transport block, transmits the packetvia an air interface, etc. FIG. 1 is a schematic diagram of a user-planeprotocol stack.

The PDCP layer generally functions to perform security-relatedoperations (e.g., encryption and decryption, integrity protection andverification, etc.), and header compression and decompression, etc. TheRLC layer generally functions to segment the data, to concatenate thedata segments, to deliver the data segments in sequence, to perform ARQoperations, etc. The MAC layer generally functions to schedule PHY-layerresources in the uplink or the downlink.

In the solution above, the RLC layer will not process any integral datapacket until the transmission time arrives, thus prolonging a period oftime for processing the data.

SUMMARY

Embodiments of the application provide a method and system fortransmitting data, and a method and system for receiving data so as toaddress the problem in the prior art that the RLC layer will not processany integral data packet until a transmission instance of time arrives,thus prolonging a period of time for processing the data.

An embodiment of the application provides a method for transmittingdata, the method including: composing, by an allocating module, RadioLink Control Protocol Data Units (RLC PDUs) from received Packet DataConvergence Protocol Data Units (PDCP PDUs), and allocatingcorresponding Radio Link Control Sequence Numbers (RLC SNs) for thecomposed RLC PDUs, wherein each RLC PDU corresponds to one RLC SN, andeach RLC PDU comprises at least one PDCP PDU; determining, by adetermining module, data corresponding to a scheduled resource from thecomposed RLC PDUs according to the size of the scheduled resource; andcomposing, by a processing module, MAC PDUs from the data correspondingto the scheduled resource, and transmitting the MAC PDUs.

Optionally allocating, by the allocating module, the corresponding RLCSNs for the composed RLC PDUs includes: allocating, by the allocatingmodule, corresponding RLC SNs in the order in which respective PDCP PDUsat the same priority are received; or allocating, by the allocatingmodule, corresponding RLC SNs in the order in which respective sets ofPDCP PDUs at the same priority are received, wherein each set of PDCPPDUs includes at least one PDCP PDU.

Optionally the allocating module allocates RLC SNs preferentially forRLC PDUs composed from PDCP PDUs at a high priority.

Optionally each composed RLC PDU comprises at least one of the receivedPDCP PDUs, and an RLC SN allocated for the composed RLC PDU; or if theorder of Packet Data Convergence Protocol Sequence Numbers (PDCP SNs) ofthe respective received PDCP PDUs is the same as the order of theallocated RLC SNs for the composed RLC PDUs, then each composed RLC PDUcomprises at least one of the received PDCP PDUs.

Optionally allocating, by the allocating module, the corresponding RLCSNs for the composed RLC PDUs includes: composing, by the allocatingmodule, the composed RLC PDUs from the received PDCP PDUs before thesize of the scheduled resource is determined; or composing, by theallocating module, the composed RLC PDUs from the received PDCP PDUsafter the size of the scheduled resource is determined.

Optionally determining, by the determining module, the datacorresponding to the scheduled resource from the composed RLC PDUsaccording to the size of the scheduled resource includes: if thedetermining module determines according to the size of the scheduledresource that segmentation is to be performed, then determining a targetRLC PDU to be segmented, according to the size of the scheduledresource, and segmenting the target RLC PDU to generate a new RLC PDU.

Optionally segmenting by the determining module, the target RLC PDU togenerate the new RLC PDU includes: generating, by the determiningmodule, the new RLC PDU according to segmentation information and datasegmented from the target RLC PDU; wherein the segmentation informationincludes a part or all of the following information: an RLC SN of thetarget RLC PDU; start positional information of the data segmented fromthe target RLC PDU in the target RLC PDU; length information of the datasegmented from the target RLC PDU; or an indicator indicating whetherthe data segmented from the target RLC PDU is the last data segment inthe target RLC PDU.

Optionally composing, by the processing module, the MAC PDUs from thedata corresponding to the scheduled data includes: ordering, by theprocessing module, RLC PDUs of the same logical channel according totheir RLC SNs, and ordering RLC PDUs of different logical channelsaccording to their priorities; and composing, by the processing module,the MAC PDUs from the ordered RLC PDUs.

Optionally composing, by the processing module, the MAC PDUs from theordered RLC PDUs includes: composing, by the processing module, the MACPPDUs according to Logical Channel IDs (LCIDs) of the ordered RLC PDUs;wherein a MAC PDU includes LCIDs of respective RLC PDUs comprised in theMAC PDU; or a MAC PDU includes different LCIDs, and there is a commonLCID for RLC PDUs corresponding to the same LCID.

Optionally each RLC PDU is an initially transmitted RLC PDU, and/or aretransmitted RLC PDU.

Optionally the allocating module, the determining module, and theprocessing module are located in the same entity; or two modules amongthe allocating module, the determining module, and the processing moduleare located in the same entity; or the allocating module, thedetermining module, and the processing module are located in differententities.

Optionally if the allocating module, the determining module, and theprocessing module are located in the same entity, then the entity is aneNB or a user equipment or a Distributed Unit (DU); or if two modulesamong the allocating module, the determining module, and the processingmodule are located in the same entity, then the allocating module islocated in a Central Unit (CU), and the determining module and theprocessing module are located in a DU.

An embodiment of the application provides a method for receiving data,the method including: separating, by a receiving module, a received MACPDU into a plurality of RLC PDUs; transmitting, by a transmittingmodule, received RLC PDUs to a parsing module; and parsing, by theparsing module, ordered and/or recombined RLC PDUs for PDCP PDUs upondetermining that the RLC PDUs can be parsed, wherein each RLC PDUcorresponds to one RLC SN, and each RLC PDU includes at least one PDCPPDU.

Optionally after the transmitting module transmits the received RLC PDUsto the parsing module, the method further includes: generating, by theparsing module, feedback information according to RLC SNs of thereceived RLC PDUs; wherein if there is a lost RLC PDU which is notsegmented, then the feedback information includes an RLC SN of the lostRLC PDU; or if there is a lost RLC PDU segment, then the feedbackinformation includes an RLC SN of an original RLC PDU comprising thelost RLC PDU segment, information indicating a start position of thelost RLC PDU segment in the original RLC PDU, and length information ofthe lost RLC PDU segment; or if there are consecutive RLC PDUs which arelost, and there is no segmented RLC PDU among the consecutive RLC PDUs,then the feedback information includes an RLC SN of the first RLC PDUamong the consecutive RLC PDUs, and the number of lost RLC PDUs; or ifthere are consecutive RLC PDUs which are lost, and there is a segmentedRLC PDU among the consecutive RLC PDUs, then the feedback informationincludes an RLC SN of the first RLC PDU among the consecutive RLC PDUs,information indicating the segmented RLC PDU, and the number of lost RLCPDUs, wherein the segmented RLC PDU is the first RLC PDU and/or the lastRLC PDU among the consecutive RLC PDUs.

Optionally transmitting, by the transmitting module, the received RLCPDUs to the parsing module includes: transmitting, by the transmittingmodule, the received RLC PDUs directly to the parsing module; orordering and/or recombining, by the transmitting module, the receivedRLC PDUs according to the RLC SNs of the received RLC PDUs, and thentransmitting the ordered and/or recombined RLC PDUs to the parsingmodule.

Optionally the receiving module, the transmitting module, and theparsing module are located in the same entity; or two modules among thereceiving module, the transmitting module, and the parsing module arelocated in the same entity; or the receiving module, the transmittingmodule, and the parsing module are located in different entities.

Optionally if the receiving module, the transmitting module, and theparsing module are located in the same entity, then the entity is an eNBor a user equipment or a DU; or if two modules among the receivingmodule, the transmitting module, and the parsing module are located inthe same entity, then the parsing module is located in a CU, and thereceiving module and the transmitting module are located in a DU.

An embodiment of the application provides a system for transmittingdata, the system including: an allocating module configured to composeRLC PDUs from received PDCP PDUs, and to allocate corresponding RLC SNsfor the composed RLC PDUs, wherein each RLC PDU corresponds to one RLCSN, and each RLC PDU includes at least one PDCP PDU; a determiningmodule configured to determine data corresponding to a scheduledresource from the composed RLC PDUs according to the size of thescheduled resource; and a processing module configured to compose MACPDUs from the data corresponding to the scheduled resource, and totransmit the MAC PDUs.

Optionally the allocating module is configured: to allocatecorresponding RLC SNs in the order in which respective PDCP PDUs at thesame priority are received; or to allocate corresponding RLC SNs in theorder in which respective sets of PDCP PDUs at the same priority arereceived, wherein each set of PDCP PDUs includes at least one PDCP PDU.

Optionally the allocating module is configured: to allocate RLC SNspreferentially for RLC PDUs composed from PDCP PDUs at a high priority.

Optionally each composed RLC PDU includes at least one of the receivedPDCP PDUs, and an RLC SN allocated for the composed RLC PDU; or if theorder of PDCP SNs of the respective received PDCP PDUs is the same asthe order of the allocated RLC SNs for the composed RLC PDUs, then eachcomposed RLC PDU includes at least one of the received PDCP PDUs.

Optionally the allocating module is configured: to compose the composedRLC PDUs from the received PDCP PDUs before the size of the scheduledresource is determined; or to compose the composed RLC PDUs from thereceived PDCP PDUs after the size of the scheduled resource isdetermined.

Optionally the determining module is configured: if it is determinedaccording to the size of the scheduled resource that segmentation is tobe performed, to determine a target RLC PDU to be segmented, accordingto the size of the scheduled resource, and to segment the target RLC PDUto generate a new RLC PDU.

Optionally the determining module is configured: to generate the new RLCPDU according to segmentation information and data segmented from thetarget RLC PDU; wherein the segmentation information includes a part orall of the following information: an RLC SN of the target RLC PDU; startpositional information of the data segmented from the target RLC PDU inthe target RLC PDU; length information of the data segmented from thetarget RLC PDU; or an indicator indicating whether the data segmentedfrom the target RLC PDU is the last data segment in the target RLC PDU.

Optionally the processing module is configured: to order RLC PDUs of thesame logical channel according to their RLC SNs, and to order RLC PDUsof different logical channels according to their priorities; and tocompose the MAC PDUs from the ordered RLC PDUs.

Optionally the processing module is configured: to compose the MACP PDUsaccording to the LCIDs of the ordered RLC PDUs; wherein a MAC PDUincludes LCIDs of the respective RLC PDUs comprised in the MAC PDU; or aMAC PDU includes different LCIDs, and there is a common LCID for RLCPDUs corresponding to the same LCID.

Optionally each RLC PDU is an initially transmitted RLC PDUs, and/or aretransmitted RLC PDU.

Optionally the allocating module, the determining module, and theprocessing module are located in the same entity; or two modules amongthe allocating module, the determining module, and the processing moduleare located in the same entity; or the allocating module, thedetermining module, and the processing module are located in differententities.

Optionally if the allocating module, the determining module, and theprocessing module are located in the same entity, then the entity is aneNB or a user equipment or a DU; or if two modules among the allocatingmodule, the determining module, and the processing module are located inthe same entity, then the allocating module is located in a CU, and thedetermining module and the processing module are located in a DU.

An embodiment of the application provides a system for receiving data,the system including: a receiving module is configured to separate areceived MAC PDU into a plurality of RLC PDUs; a transmitting module isconfigured to transmit received RLC PDUs to a parsing module; and theparsing module is configured to parse ordered and/or recombined RLC PDUsfor PDCP PDUs upon determining that the RLC PDUs can be parsed, whereineach RLC PDU corresponds to one RLC SN, and each RLC PDU includes atleast one PDCP PDU.

Optionally the parsing module is further configured: to generatefeedback information according to RLC SNs of the received RLC PDUs;where if there is a lost RLC PDU which is not segmented, then thefeedback information includes an RLC SN of the lost RLC PDU; or if thereis a lost RLC PDU segment, then the feedback information includes an RLCSN of an original RLC PDU comprising the lost RLC PDU segment,information indicating a start position of the lost RLC PDU segment inthe original RLC PDU, and length information of the lost RLC PDUsegment; or if there are consecutive RLC PDUs which are lost, and thereis no segmented RLC PDU among the consecutive RLC PDUs, then thefeedback information includes an RLC SN of the first RLC PDU among theconsecutive RLC PDUs, and the number of lost RLC PDUs; or if there areconsecutive RLC PDUs which are lost, and there is a segmented RLC PDUamong the consecutive RLC PDUs, then the feedback information includesan RLC SN of the first RLC PDU among the consecutive RLC PDUs,information indicating the segmented RLC PDU, and the number of lost RLCPDUs, wherein the segmented RLC PDU is the first RLC PDU and/or the lastRLC PDU among the consecutive RLC PDUs.

Optionally the transmitting module is configured: to transmit thereceived RLC PDUs directly to the parsing module; or to order and/orrecombine the received RLC PDUs according to the RLC SNs of the receivedRLC PDUs, and then transmit the ordered and/or recombined RLC PDUs tothe parsing module.

Optionally the receiving module, the transmitting module, and theparsing module are located in the same entity; or two modules among thereceiving module, the transmitting module, and the parsing module arelocated in the same entity; or the receiving module, the transmittingmodule, and the parsing module are located in different entities.

Optionally if the receiving module, the transmitting module, and theparsing module are located in the same entity, then the entity is an eNBor a user equipment or a DU; or if two modules among the receivingmodule, the transmitting module, and the parsing module are located inthe same entity, then the parsing module is located in a CU, and thereceiving module and the transmitting module are located in a DU.

An embodiment of the application provides a transmitting deviceincluding: a processor configured to read and execute program in amemory: to compose RLC PDUs from received PDCP PDUs, and to allocatecorresponding RLC SNs for the composed RLC PDUs, wherein each RLC PDUcorresponds to one RLC SN, and each RLC PDU includes at least one PDCPPDU; to determine data corresponding to a scheduled resource from thecomposed RLC PDUs according to the size of the scheduled resource; andto compose MAC PDUs from the data corresponding to the scheduledresource, and to transmit the MAC PDUs; and a transceiver configured toreceive and transmit data under the control of the processor.

An embodiment of the application provides a receiving device including:a processor configured to read and execute program in a memory: toseparate a received MAC PDU into a plurality of RLC PDUs; to transmitreceived RLC PDUs to a parsing module; and to parse ordered and/orrecombined RLC PDUs for PDCP PDUs upon determining that the RLC PDUs canbe parsed, wherein each RLC PDU corresponds to one RLC SN, and each RLCPDU includes at least one PDCP PDU; and a transceiver configured toreceive and transmit data under the control of the processor.

In the embodiments of the application, RLC PDUs are composed fromreceived PDCP PDUs, and corresponding RLC SNs are allocated for thecomposed RLC PDUs, where each RLC PDU corresponds to one RLC SN, andeach RLC PDU includes at least one PDCP PDU; data corresponding to ascheduled resource are determined from the composed RLC PDUs accordingto the size of the scheduled resource; and MAC PDUs are composed fromthe data corresponding to the scheduled resource and transmitted. In theembodiments of the application, a binding relationship is createdbetween the PDCP PDUs and the RLC PDUs, and each RLC PDU includes atleast one PDCP PDU, so that the allocating module can generate the RLCPDUs upon reception of a part of the PDCP PDUs to thereby shorten thelength of time for processing layer-2 data packets.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to make the technical solutions according to the embodiments ofthe application more apparent, the drawings to which reference is madeto in the description of the embodiments will be introduced below inbrief, and apparently the drawings to be described below are only someembodiments of the application, and those ordinarily skilled in the artcan further derive other drawings from these drawings without anyinventive effort.

FIG. 1 is a schematic diagram of a user-plane protocol stack in theprior art.

FIG. 2 is a schematic flow chart of a method for transmitting dataaccording to an embodiment of the application.

FIG. 3A is a schematic diagram of a first packaging scheme according toan embodiment of the application.

FIG. 3B is a schematic diagram of a second packaging scheme according toan embodiment of the application.

FIG. 3C is a schematic diagram of a third packaging scheme according toan embodiment of the application.

FIG. 4A is a schematic diagram of downlink data transmission when a CUis separate from a DU according to an embodiment of the application.

FIG. 4B is a schematic diagram of uplink data transmission when a CU isseparate from a DU according to an embodiment of the application.

FIG. 5 is a schematic flow chart of a method for receiving dataaccording to an embodiment of the application.

FIG. 6 is a schematic structural diagram of a system for transmittingdata according to an embodiment of the application.

FIG. 7 is a schematic structural diagram of a system for receiving dataaccording to an embodiment of the application.

FIG. 8 is a schematic structural diagram of a transmitting deviceaccording to an embodiment of the application.

FIG. 9 is a schematic structural diagram of a receiving device accordingto an embodiment of the application.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In order to make the objects, the technical solutions, and theadvantages of the application more apparent, the application will bedescribed below in further details with reference to the drawings.Apparently the embodiments to be described are only a part but not allof the embodiments of the application. Based upon the embodiments of theapplication, all the other embodiments which can occur to thoseordinarily skilled in the art without any inventive effort shall fallinto the claimed scope of the application.

As illustrated in FIG. 2, a method for transmitting data according to anembodiment of the application includes the following steps.

In the step 200, an allocating module composes RLC PDUs from receivedPDCP PDUs, and allocates corresponding RLC SNs for the composed RLCPDUs, where each RLC PDU corresponds to one RLC SN, and each RLC PDUincludes at least one PDCP PDU.

In the step 201, a determining module determines data corresponding to ascheduled resource from the composed RLC PDUs according to the size ofthe scheduled resource.

In the step 202, a processing module composes MAC PDUs from the datacorresponding to the scheduled resource, and transmits the MAC PDUs.

In the embodiments of the application, RLC PDUs are composed fromreceived PDCP PDUs, and corresponding RLC SNs are allocated for thecomposed RLC PDUs, where each RLC PDU corresponds to one RLC SN, andeach RLC PDU includes at least one PDCP PDU; data corresponding to ascheduled resource are determined from the composed RLC PDUs accordingto the size of the scheduled resource; and MAC PDUs are composed fromthe data corresponding to the scheduled resource and transmitted. In theembodiments of the application, a binding relationship is createdbetween the PDCP PDUs and the RLC PDUs, and each RLC PDU includes atleast one PDCP PDU, so that the allocating module can generate the RLCPDUs upon reception of a part of the PDCP PDUs to thereby shorten thelength of time for processing layer-2 data packets.

In an implementation, the number of PDCP PDUs in each RLC PDU can beconfigured by a higher layer (for example, the number of PDCP PDUs ineach RLC PDU, or the largest number of bytes in each RLC PDU can beconfigured), that is, configured statically; or can be configureddynamically by the allocating module according to a dynamic linkcondition and/or load condition (for example, the number of PDCP PDUs ineach RLC PDU, or the largest number of bytes in each RLC PDU can beconfigured).

For example, when there are a good link condition and a low load, alarger number of PDCP PDUs in each RLC PDU can be set, and when there isa poor link condition or a high load, a smaller number of PDCP PDUs ineach RLC PDU can be set.

If the allocating module, the determining module, and the processingmodule are not located in the same entity, then since the link conditionand the load condition are statistically determined by the determiningmodule, if the allocating module is located in a CU, and the determiningmodule and the processing module are located in a DU, then the DU willfeed the related conditions to the CU so that the determining module inthe CU configures the number of PDCP PDUs in each RLC PDU. Moreover whena bearer of a UE is transmitted through a plurality of DUs, then sincethe states of the respective DUs may be different from each other, theallocating module in the CU may apply different dynamic configurationsto the respective DUs according to different conditions of therespective DUs.

When a one-to-one mapping relationship between the RLC PDUs and the PDCPPDUs is configured, each PDCP PDU corresponds to one RLC PDU; and whenan RLC PDU can include a plurality of PDCP PDUs, the number N of PDCPPDUs in an RLC PDU can be configured, and/or the size of an RLC PDU canbe configured as M bytes, that is, no more than M bytes can be includedin an RLC PDU.

If the number N of PDCP PDUs in an RLC PDU is configured, then an RLCPDU will be composed from N consecutive PDCP PDUs, and allocated with anRLC SN; and if the size of an RLC PDU is configured as M bytes, then anRLC PDU will be composed from several consecutive PDCP PDUs having nomore than M bytes. Optionally the RLC PDU is composed from consecutivePDCP PDUs having maximum bytes, but the total size of the consecutivePDCP PDUs is no more than M.

In a particular implementation, when an RLC PDU includes a plurality ofPDCP PDUs, the plurality of PDCP PDUs are located in the same RLC PDU,and correspond to the same RLC SN. Stated otherwise, several PDCP PDUsare combined in advance into an integral RLC PDU to be processed. Inthis implementation, the PDCP PDUs are small packets, that is, if therespective packets are processed separately, then both a header overheadand a processing overhead will be considerate, so they can beconcatenated in advance into an RLC PDU with a moderate size to therebylower the header overhead and the processing overhead.

RLC PDUs can be subsequently processed in the same way regardless of thenumber of PDCP PDUs in an RLC PDU.

In the embodiment of the application, after data packets arrive at thePDCP layer, a discard timer will be started for each data packet, and ifthe data packet has not been processed and transmitted after the timerexpires, then it may be deleted directly; and the length of the timercan be Radio Resource Control (RRC)-configured, and the length thereofis related to the Quality of Service (QoS) of a service, and generallydetermined by the longest transmission delay tolerable to the service.

Generally the PDCP layer can buffer received higher-layer data, or canprocess the data immediately as follows: for each data packet from thehigher layer, a Sequence Number (SN) is allocated in order, where theinitial value of the SN is 0, that is, the SN allocated for the firstService Data Unit (SDU) is 0, the SN allocated for the second SDU is 1,and so on; a configured requirement is followed, and for example, ifrequired header compression is configured, then a header compressionprocess will be performed according to a configured header compressionprotocol; a security requirement is followed, and for example, integrityprotection and security operations are performed on the data packet, andgenerally the integrity protection operation is only performed oncontrol-plane data, and all the data including control-plane data anduser-plane data are encrypted; a necessary PDCP header is added, wherethe PDCP header generally includes a PDCP SN, a PDCP PDU type indicator,etc.; and the data packet is transmitted to a corresponding RLCtransmitting entity.

When the allocating module receives the data packets from the PDCPlayers, i.e., the RLC SDUs, generally it firstly stores them into atransmission buffer, and forms RLC PDUs and transmits the RLC PDUs tothe processing module on an appropriate occasion, so that they areprocessed at the MAC and PHY layers, and then transmitted via an airinterface.

In the embodiment of the application, the allocating module, thedetermining module, and the processing module are located in the sameentity; or two modules among the allocating module, the determiningmodule, and the processing module are located in the same entity; or theallocating module, the allocating module, the determining module, andthe processing module are located in different entities.

If the allocating module, the determining module, and the processingmodule are located in the same entity, then the entity will be an eNB ora UE or a DU; or if two modules among the allocating module, thedetermining module, and the processing module are located in the sameentity, then the allocating module will be located in a CU, and thedetermining module and the processing module will be located in a DU.

I. For the sake of a convenient description, the inventive solution willbe described below by way of an example in which all of three User-Plane(UP) entities including the allocating module, the determining module,and the processing module are located in the same physical entity, orconnected over an ideal backhaul (with a transmission delay far below amillisecond order).

Implementations in which two modules among the allocating module, thedetermining module, and the processing module are located in the sameentity or different entities, or the allocating module, the determiningmodule, and the processing module are connected over a non-idealbackhaul will be described later.

The allocating module stores received PDCP PDU into a transmissionbuffer in order.

Optionally if there are different priority labels of these data packets,then data packets at different priorities will be buffered separately,that is, data packets at the same priority are buffered in a queue inthe order in which they are received, and there are different queues ofdata packets at different priorities.

The allocating module allocates corresponding RLC SNs in the order inwhich respective PDCP PDUs at the same priority are received; or theallocating module allocates corresponding RLC SNs in the order in whichrespective sets of PDCP PDUs at the same priority are received, whereeach set of PDCP PDUs includes at least one PDCP PDU.

If there is a one-to-one correspondence relationship between the PDCPPDUs and the RLC PDUs, then the allocating module may allocatecorresponding RLC SNs for the respective PDCP PDUs in the order of thePDCP PDUs, and for example, allocate 0 for the first PDCP PDU, 1 for thesecond PDCP PDU, and so on.

Here the SN of a PDCP PDU may be equal to the SN of an RLC PDUcorresponding thereto, and for example, if there is a one-to-onecorrespondence relationship between the PDCP PDUs and the RLC PDUs, thenthe PDCP SNs 0, 1, 2, 3, 4, . . . will be the same as the RLC SNs 0, 1,2, 3, 4, . . . , and at this time, the RLC SNs may be omitted, but thePDCP SNs may be reused directly as the RLC SNs to perform a related RLCoperation, that is, if the order of the PDCP SNs of the respectivereceived PDCP PDUs is the same as the order of the RLC SNs correspondingto the respective PDCP PDUs, then each composed RLC PDU will include atleast one PDCP PDU.

Alternatively the PDCP SNs may be discrete, and for example, if a beareris allocated to two paths for transmission, then the PDCP SNs of thePDCP PDUs received by an RLC transmitting entity may be PDCP SNs 0, 2,4, 6, 9, . . . , mapped respectively in order to RLC SNs 0, 1, 2, 3, 4,. . . ; or a PDCP PDU may be deleted upon expiration, so the PDCP SNsmay be discrete, and for example, the PDCP SNs of the PDCP PDUs receivedby an RLC entity may be PDCP SNs 0, 1, 2, 5, 6, 7, . . . , mappedrespectively in order to RLC SNs 0, 1, 2, 3, 4, 5, . . . . If an RLC PDUincludes a plurality of PDCP PDUs, for example, an RLC PDU includes twoPDCP PDUs, then PDCP SNs 0 and 1 will be mapped to an RLC SN 0, PDCP SNs2 and 3 will be mapped to an RLC SN 1, and so on. That is, each composedRLC PDU includes at least one PDCP PDU, and an RLC SN allocated for thePDCP PDU.

In an implementation, data packets shall be transmitted in order at theRLC layer, so the RLC SNs shall be allocated consecutively in order, andwhen this is satisfied by the PDCP SNs at the RLC layer, the PDCP SNscan be reused to thereby save a header overhead; and when all the PDCPSNs are not consecutive in order, consecutive SNs can be allocatedseparately at the RLC layer. A particular decision can be made basedupon the RRC configuration, that is, whether there are RLC SNs isdetermined by the RRC configuration.

In the example above, there is a one-to-one correspondence relationshipbetween the PDCP PDUs and the RLC PDUs, but there may be aone-to-multiple correspondence relationship between them in animplementation as long as this mapping relationship can be recorded inthe allocating module, and for example, a fixed number N of PDCP PDUsare mapped to one RLC PDU, or PDCP PDUs of no more than M bytes can bemapped to one RLC PDU. For example, the allocating module can compose anRLC PDU from every two received PDCP PDUs; or can compose some RLC PDUfrom one PDCP PDU, some RLC PDU from two PDCP PDUs, some RLC PDU fromthree PDCP PDUs, etc.

Here the processing module transmits the size of a scheduled resource,e.g., N bytes, after scheduling the resource. In an implementation, whenthere is only one prioritized queue, the allocating module can allocatethe RLC SNs one by one upon reception of the PDCP-layer data, and formthe RLC PDUs (that is, the allocating module composes the RLC PDUs fromthe received PDCP PDUs before the size of the scheduled resource isdetermined); and when there are a plurality of prioritized queues, theallocating module can allocate the SNs in real time upon reception ofthe size of the scheduled resource (that is, the allocating moduleallocates corresponding RLC SNs preferentially for PDCP PDUs at a higherpriority, and for example, if there is a higher priority of aprioritized queue A than a prioritized queue B, then corresponding RLCSNs will be allocated preferentially for the queue A), and form the RLCPDUs (that is, the allocating module composes the RLC PDUs from thereceived PDCP PDUs after the size of the scheduled resource isdetermined). High real-time processing efficiency is not required in theformer implementation, and background processing can be performed inanother optional implementation. When there are a plurality of differentprioritized queues at the RLC layer, the RLC SDUs can be processed undersome prioritization principle instead of the first-come-first-served,and at this time, the RLC SNs cannot be allocated, and the RLC PDUscannot be composed, in advance, but after the processing module notifiesthe scheduled resource, those RLC PDUs to be transmitted are determinedin an order of their priorities, and at this time, the RLC SNs can beallocated for the RLC SDUs, and the RLC PDUs can be composed from theRLC SDUs.

After the determining module determines the size of the scheduledresource (for example, the processing module at the MAC layer notifiesthe determining module of the size of the scheduled resource), theamount of data to be transmitted to the processing module can bedetermined in real time according to the size of the scheduled resource,and for example, if the size of the first RLC PDU is 200 bytes, the sizeof the second RLC PDU is 300 bytes, the size of the third RLC PDU is 500bytes, and the size of the scheduled resource is 800 bytes, then boththe first and second RLC PDUs (500 bytes in total) will be transmittedto the processing module, and the first 300 bytes in the third RLC PDUwill be taken as a RLC PDU segment transmitted to the processing module.

Stated otherwise, if the determining module decides to segment an RLCPDU, according to the size of the scheduled resource, then it willdetermine a target RLC PDU to be segmented, according to the size of thescheduled resource, segment the target RLC PDU, and generate a new RLCPDU (which can be referred to as an RLC PDU segment).

Optionally the determining module generates the new RLC PDU according tosegmentation information and data segmented from the target RLC PDU.

Here the segmentation information includes a part or all of thefollowing information: the RLC SN of the target RLC PDU; startpositional information of the data segmented from the target RLC PDU inthe target RLC PDU; length information of the data segmented from thetarget RLC PDU; and an indicator indicating whether the data segmentedfrom the target RLC PDU is the last data segment in the target RLC PDU.

For example, the format of the RLC PDU segment is as follows: optionallyan RLC SN shall be carried, and for the same RLC PDU, different segmentsthereof shall carry the same SN, that is, they correspond to theoriginal RLC PDU; optionally a start position, a Segment Offset (SO), ofthe RLC PDU segment in the original RLC PDU shall be carried, and forexample, if the RLC PDU segment is the first segment, then the startposition will be 0, and if the RLC PDU segment is bytes 300 to 500 inthe RLC PDU, then the start position will be 300; optionally the RLCsegment shall carry the length of the segment, and for example, if theRLC segment is a segment of bytes 0 to 200 in the original RLC PDU, thenthe length thereof will be 200 bytes, and the length filed is optionalin a header field of the RLC segment because the length may be reflectedwhen an MAC packet is generated; and optionally a Last Segment Flag(LSF) indicating whether the RLC PDU segment is the last segment shallbe carried, for example, as a 1-bit explicit indicator, where 0indicates that it is not the last segment, and 1 indicates that it isthe last segment.

Here an RLC PDU in the embodiment of the application can be an initiallytransmitted RLC PDU and/or a retransmitted RLC PDU.

In an implementation, no matter whether an RLC PDU is retransmitted orinitially transmitted, if the size of the scheduled resource is notsufficient to accommodate the entire RLC PDU, then the RLC PDU may besegmented according to the size of the scheduled resource to therebyimprove the transmission efficiency and avoid a transmission resourcefrom being wasted.

Here an RLC PDU segment may be retransmitted in the following twoinstances: retransmission of an RLC PDU is requested, but thetransmission resource is not sufficient to accommodate the entire RLCPDU, so the RLC PDU shall be segmented according to the size of theresource; and retransmission of an RLC PDU segment is requested, but thetransmission resource is not sufficient to accommodate the entirerequested RLC PDU segment, so the RLC PDU shall be segmented againaccording to the size of the resource.

In either of the instances above, for an RLC PDU segment to beretransmitted, the retransmitted RLC PDU segment is similar to aninitially transmitted segment, that is, the RLC SN indicates the RLC PDUincluding the segment, and SO, LI, and LSF indicate the position and thelength of the segment in the original RLC PDU, and whether the segmentis the last segment.

By way of an example, an RLC PDU segment to be retransmitted ispositioned at bytes 500 to 1500 in an RLC PDU with an SN of 10, and thetotal length of the RLC PDU is 1500 bytes. The size of a resource on afirst transmission occasion is 700 bytes, so the RLC PDU segment issegmented according to the size of the transmission resource, where theSN of the RLC PDU is 10, the SO thereof is 500, the LI thereof is 700,and the LSF thereof is 0 (the segment is not the last segment); and thesize of a resource on a second transmission occasion is 300 bytes, sothe RLC PDU segment is segmented according to the size of thetransmission resource, where the SN of the RLC PDU is 10, the SO thereofis 1200, the LI thereof is 300, and the LSF thereof is 1 (the segment isthe last segment).

For a receiver, since reception of the bytes 0 to 499 in the RLC PDUwith the SN of 10 has been acknowledged, and reception of the remainingbytes thereof has been negatively acknowledged, it is determined thatthe entire RLC PDU with the SN of 10 has been received, upon receptionof the two retransmissions in that the PDU has been received correctlybecause all the bytes thereof have been received in order until the lastsegment.

Optionally the processing module composes the MAC PDUs from the datacorresponding to the scheduled resource in such a way that it orders RLCPDUs of the same logical channel according to their RLC SNs, orders RLCPDUs of different logical channels according to their priorities, andcomposes the MAC PDUs from the ordered RLC PDUs.

Here the MAC PDUs are composed under the following principle: RLC PDUsand RLC PDU segments from the same logical channel are combined togetherin an order of their SNs or priorities as many as possible; and for dataof different logical channels, data of a logical channel at a highpriority are placed in earlier bytes of an MAC PDU, and data of alogical channel at a low priority are placed in later bytes of the MACPDU, as many as possible, that is, the data of the logical channels areplaced in an order of their priorities.

FIG. 3A illustrates a typical packaging process, where the P-SNrepresents a PDCP SN, the R-SN represents an RLC SN, the LCID representsa Logical Channel Identifier, and the LI represents a Length Indicatingfield. Since there is a higher priority data of the logical channel withthe LCID1 than data of the logical channel with the LCID2, the data canbe placed in earlier bytes of an MAC PDU, and RLC PDUs of the samelogical channel are placed together as many as possible. Since data ofthe logical channel with the LCID2 are a segment, which is the firstsegment, so the Segment Offset (SO) is 0. Here there is anothersimplified scheme in which a 1-bit indicator indicates that this is asegment, which is the first segment; and for the second segment of thelogical channel with the LCID2, an explicit SO indicator shall becarried.

For example, the first segment is transmitted over the logical channelwith the LCID2 at an instant 1 of time, and since this segment startswith the initial position of the original RLC PDU with the SN of n, SO=0can be carried to indicate that this is the first segment, or a specialbit segment (First Segment (FS)), e.g., 1-bit information, can becarried, where the FS taking the value of 1 indicates that this is thefirst segment, and the FS taking the value of 0 indicates that this isnot the first segment. When it is the first segment, since the carriedFS=1 explicitly indicates that this is the first segment, SO=0 may beomitted at this time.

The second segment in the same RLC PDU with the SN of n, of the logicalchannel with the LCID2, shall be transmitted at the next transmissioninstant 2 of time, and at this time, it is not the first segment, soexplicit SO shall be carried to indicate the start position of thesecond segment in the original RLC PDU.

In an implementation, the processing module composes the MACP PDUsaccording to the LCIDs of the ordered RLC PDUs.

Here a MAC PDU includes LCIDs of respective RLC PDUs comprised in theMAC PDU.

In another optional implementation, a MAC PDU includes different LCIDs,and there is a common LCID for RLC PDUs corresponding to the same LCID.Particularly in the example as illustrated in FIG. 3B, data packets withthe same LCID are combined together, and carry the uniform LCID.

In the two examples above, the allocating module and the determiningmodule are located at the RLC layer, and the processing module islocated at the MAC layer. For the sake of further simplification, all ofthe allocating module, the determining module, and the processing modulecan be arranged at the MAC layer particularly as illustrated in FIG. 3C.

In an implementation, the processing module can process data processedby the determining module, and the determining module processessubsequent data concurrently to thereby save a processing period oftime, and for example, the determining module can transmit processed MACPDUs to the processing module for further processing, and also thedetermining module can further process subsequent MAC PDUs.

It shall be noted that in the description above, only some fields areillustrated in a header format of each layer, e.g., SN, LI, LCID, etc.,but in a particular implementation, there may be also other fields inthe header, e.g., a type indicator D/C indicating data or control, an Efield which is an extension indicating field, LS indicating the lastsegment, etc., although a repeated description thereof will be omittedhere.

II. Implementations in which two modules among the allocating module,the determining module, and the processing module are located in thesame entity or different entities, or the allocating module, thedetermining module, and the processing module are connected over anon-ideal backhaul will be described below.

Here, for example, the allocating module is located in a CU, and thedetermining module and the processing module are located in a DU.

FIG. 4A illustrates typical processing of downlink data in a CU/DUentity.

Here the CU refers to a central processing entity, and the DU is adistributed processing entity.

The RLC-H refers to the allocating module, the RLC-L refers to thedetermining module, and they are located respectively two physicalentities, i.e., a CU and a DU.

Downlink data are transmitted as follows.

1. The PDCP layer allocates PDCP SNs for higher-layer data, performs ansecurity operation and header compression on the data, and adds headersto the data, to generate PDCP PDUs, and transmits them to acorresponding RLC-H entity.

2. The RLC-H entity allocates RLC SNs for received PDCP PDUs in order,where there is a one-to-one correspondence relationship between RLC PDUsand the PDCP PDUs, and distributes the data and the corresponding RLCSNs to one or more RLC-L entities.

Here a path with a better link condition and a lower load is selectedaccording to flow control and feedback, or in order to satisfy arequired short transmission delay and high reliability, the same datacan be transmitted to a plurality of RLC-L entities at the same time.

3. The RLC-L entity or entities in a DU combines and transmits RLC PDUsand RLC PDU segments with an appropriate size to the MAC layer forsubsequent transmission, according to the size of a transmissionresource scheduled in real time by the MAC layer, where an RLC PDUsegment carries the RLC SN allocated by the RLC-H entity, and SO, LI,LSF, and other indicating fields according to its original PDCP PDU.

In the embodiment of the application, the data are processed at theMAC/PHY layer, and then transmitted via an air interface, and furtherprocessed at the opposite PHY/MAC layer, delivered to the receivingRLC-L entity or entities, and converged onto the RLC-H entity, so thatthe RLC-H entity updates and feeds back a reception state, andrecomposes and delivers the data packets to the PDCP layer. The PDCPlayer supports out-of-order de-securing, header decompression, and otheroperations.

Optionally here the RLC-L entity or entities firstly recomposes orrecompose the RLC PDUs, and then delivers or deliver them to the RLC-Hentity, or the RLC-L entity or entities delivers or deliver the RLC PDUsegments directly to the RLC-H entity, and finally the RLC-H entityrecomposes and orders them. Generally when the same RLC PDUs aretransmitted over respective paths, the RLC-H entity can recombine RLCPDU segments from the different paths to thereby speed up recombinationand shorten a delay. Accordingly when the same data are transmitted overa plurality of paths, the function of recombining RLC PDU segments canbe performed by the RLC-H entity; otherwise, this function can beperformed by the RLC-L entity or entities, that is, the function can beperformed flexibly.

Furthermore in the embodiment of the application, only a typical exampleof a user-plane protocol stack disturbed between a CU and a DU, but infact, the method for processing data according to the embodiment of theapplication can also be performed similarly when only the PDCP entity islocated in the CU, and both the RLC entity and the MAC entity arelocated in the DU, or the PDCP entity and a plurality of RLC-H entitiesare located in the CU, and both a plurality of RLC-L entities and theMAC entity are located in the DU, although a repeated descriptionthereof will be omitted here.

As illustrated in FIG. 5, a method for receiving data according to anembodiment of the application includes the following steps.

In the step 500, a receiving module separates a received MAC PDU into aplurality of RLC PDUs.

In the step 501, a transmitting module transmits received RLC PDUs to aparsing module.

In the step 502, the parsing module parses ordered and/or recombined RLCPDUs for PDCP PDUs upon determining that the RLC PDUs can be parsed,where each RLC PDU corresponds to one RLC SN, and each RLC PDU includesat least one PDCP PDU.

In the embodiment of the application, the receiving module, thetransmitting module, and the parsing module are located in the sameentity; or two modules among the receiving module, the transmittingmodule, and the parsing module are located in the same entity; or thereceiving module, the transmitting module, and the parsing module arelocated in different entities.

If the receiving module, the transmitting module, and the parsing moduleare located are located in the same entity, then the entity will be aneNB or a UE or a DU.

If two modules among the receiving module, the transmitting module, andthe parsing module are located in the same entity, then the parsingmodule will be located in a CU, and the receiving module and thetransmitting module are located in a DU.

I. For the sake of a convenient description, the inventive solution willbe described below by way of an example in which all of three User-Plane(UP) entities including the receiving module, the transmitting module,and the parsing module are located in the same physical entity, orconnected over an ideal backhaul (with a transmission delay far below amillisecond order).

Implementations in which two modules among the receiving module, thetransmitting module, and the parsing module are located in the sameentity or different entities, or the allocating module, the determiningmodule, and the processing module are connected over a non-idealbackhaul will be described later.

The receiver performs an inverse process of the transmitter. Uponreception of data from the physical layer via an air interface, thereceiver processes the data at the physical layer, and then recovers thedata into the format of an MAC PDU.

Upon reception of the data, the receiver parses the data for differentdata blocks according to LCID, LI, and other information carriedtherein, and determines RLC PDUs of different logical channels accordingto the indicating LCIDs (the RLC PDUs may also include an RLC PDUsegment).

The transmitting module processes the RLC PDUs in the following twoimplementations upon reception of the RLC PDUs.

In a first implementation, the transmitting nodule transmits thereceived RLC PDUs directly to the parsing module.

In this implementation, upon reception of the RLC PDUs, the transmittingmodule delivers the RLC PDUs to the parsing module, and also an RLC PDUsegment directly to the parsing module.

In fact, the first implementation is similar to atransparent-transmission implementation, that is, all of the receiveddata are transmitted directly to a RLC Higher module (i.e., the parsingmodule) for processing, e.g., gap detection, a Treordering timer,ACK/NACK state feedback, etc.

In a second implementation, the transmitting module reorders and/orrecombines and then transmits the received RLC PDUs to the parsingmodule according to RLC SNs of the received RLC PDUs.

The transmitting module reorders the received RLC PDUs, and recombinesand then reorders RLC PDU segments to thereby avoid them from being outof order due to an MAC HARQ, and delivers them to the parsing module.

If there are discretely received RLC PDUs, then Treordering_timer willbe started, and if no integral RLC PDUs have been received yet afterTreordering_timer expires, then the RLC PDUs detected untilTreordering_timer expires will be delivered to the parsing module, orwill not be delivered to the parsing module until integral RLC PDUs arereceived.

Here the RLC PDUs are ordered by updating a reception state in an orderof their RLC SNs, and for example: if the highest SN of the datacurrently received in order is 3, then the next SN to the highest SNwill be 4, and if the SN of a newly received RLC PDU is 4, that is, theRLC PDU is received in order, then the next SN to the highest SN of thedata received in order will be updated to 5 (of course, here only thehighest SN may be recorded without recording the next SN to the highestSN); and if there is an SN gap occurring among the RLC SNs (for example,if the SN of a received RLC PDU is 3, and the next SN is 5, then an SNgap will be determined), then Treordering_timer may be started, and anout-of-order condition due to underlying transmission may be detected,and if no PDU has been received after Treordering_timer expires, then await will be aborted (in the Unacknowledged Mode (UM)), or the parsingmodule will feed back an NACK state report to request for retransmission(in the Acknowledged Mode (AM)).

Here after the transmitting module transmits the received RLC PDUs tothe parsing module, the parsing module generates feedback informationaccording to the RLC SNs of the received RLC PDUs. Thereafter thefeedback information can be transmitted as in the method according tothe embodiment of the application.

Different feedback information is made in different reception instancesas described below respectively.

In a first instance, if there is no SN gap occurring, that is, the RLCPDUs are received successfully, then the feedback information willinclude Acknowledgement (ACK) information.

In a second instance, if there is an SN gap occurring, that is, there isa lost RLC PDU or PDUs, then the feedback information will includeNegative Acknowledgement (NACK) information.

For the feedback information for an SN gap occurring, since RLC PDU dataare allowed to be segmented according to the size of the transmissionresource, the gap may occur because the entire RLC PDU is lost, or anRLC PDU segment is lost, or a series of consecutive RLC PDUs are lost.

The NACK state shall be reported while considering high efficiency andsaving an overhead so that a lost RLC PDU is indicated explicitly withNACK_SN, a lost RLC PDU segment is indicated explicitly with NACK_SNcarrying SO and LI, and a plurality of lost RLC PDUs with consecutiveSNs are indicated explicitly with the first NACK_SN carrying the numberof consecutive PDUs which are lost. Only the NACKed RLC PDUs shall beindicated one by one, and there will be only one ACK_SN to indicate thatall of the other PDUs with the ACK_SN than the PDUs or PDU segmentsindicated explicitly with NACK are received correctly.

The feedback information for an SN gap occurring will be describedbelow.

1. If there is a lost RLC PDU which is not segmented, then the feedbackinformation will include the RLC SN of the lost RLC PDU.

For example, if the SN of a received RLC PDU is 3, and the SN of thenext received RLC PDU is 5, then it will be determined that an RLC PDUwith the SN of 4 is lost, and 4 may be added to the feedbackinformation.

2. If there is a lost RLC PDU segment, then the feedback informationwill include the RLC SN of the original RLC PDU including the lost RLCPDU segment, information indicating the start position of the lost RLCPDU segment in the original RLC PDU, and length information of the lostRLC PDU segment.

For example, the SN of a received RLC PDU segment is 3, the SN of thenext received RLC PDU is 4, and the RLC PDU with the SN of 3 can bedetermined as a segmented RLC PDU, and the particular segment which isnot received can be determined, according to the received RLC PDUsegment with the SN of 3; and for example, if the first segment is notreceived, and the length of the lost RLC PDU segment is 200 bytes, thenthe feedback information will include SN=3, and Length=200, and alsoSO=0 indicating the start position of the lost RLC PDU segment in theoriginal RLC PDU, or FS=1 indicating the first segment. Optionally thelength can be indicated in the Length Indicator, or can be representedas the end position of the segment in the original RLC PDU.

3. If there are consecutive RLC PDUs which are lost, and there is nosegmented RLC PDU among the consecutive RLC PDUs, then the feedbackinformation will include the RLC SN of the first RLC PDU among theconsecutive RLC PDUs, and the number of lost RLC PDUs.

For example, if the SN of a received RLC PDU is 3, and the SN of thenext received RLC PDU is 7, then it will be determined that RLC PDUswith the SNs of 4, 5, and 6 are lost, so the feedback informationincludes 4 (i.e., the RLC SN of the first RLC PDU) and 3 (i.e., thenumber of lost RLC PDUs).

4. If there are consecutive RLC PDUs which are lost, and there is asegmented RLC PDU among the consecutive RLC PDUs, then the feedbackinformation will include the RLC SN of the first RLC PDU among theconsecutive RLC PDUs, information indicating the segmented RLC PDU, andthe number of lost RLC PDUs, where the segmented RLC PDU is the firstRLC PDU and/or the last RLC PDU among the consecutive RLC PDUs.

For example, if a part of an original RLC PDU with the SN of 4 isreceived, and the SN of the next received RLC PDU is 7, then it will bedetermined that RLC PDUs with the SNs of 4, 5, and 6 are lost. If theRLC PDU with the SN of 4 among the RLC PDUs with the SNs of 4, 5, and 6is a segmented RLC PDU, then the feedback information will include 4(i.e., the RLC SN of the first RLC PDU), 3 (i.e., the number of lost RLCPDUs), and information indicating the segmented RLC PDU (e.g., 00indicates the first RLC PDU is segmented, 01 indicates the last RLC PDUis segmented, and 11 indicates the first and last RLC PDUs aresegmented).

The receiver makes feedback only according to a reception state, and ifthe entire RLC PDU is not received (even if the RLC PDU is segmented),then the SN may characterize the entire lost RLC PDU; and if a part ofsegments of the RLC PDU are received, then a state report will carrysegment information of the lost RLC PDU segments.

Here if information about consecutive RLC PDUs which are lost is to befed back, then there will be no segmented RLC PDU among the consecutiveRLC PDUs which are lost, or the first RLC PDU and/or the last RLC PDUwill be a segmented PDU; and if there is a segmented RLC PDU among theconsecutive RLC PDUs which are lost, and the segmented RLC PDU is notthe first RLC PDU or the last RLC PDU, then the first and secondimplementations may be applied, that is, the RLC PDUs which are notsegmented, and the segmented RLC PDU are fed back separately, or the RLCPDUs satisfying the requirement may be fed back consecutively, and theother RLC PDUs will be fed back separately.

For example, if RLC PDUs with the SNs of 3 to 8 are lost, where the RLCPDU with the SN of 7 is a segmented RLC PDU, then the RLC PDUs with theSNs of 3 to 6 may be fed back consecutively, and the RLC PDUs with theSNs of 7 and 8 may be fed back separately; or the RLC PDUs with the SNsof 3 to 6 may be fed back consecutively, and the RLC PDUs with the SNsof 7 and 8 may be fed back consecutively.

In an implementation, when the entire RLC PDU is received in a receptionwindow, even if it is not an RLC PDU received in order, then the parsingmodule may parse the RLC PDU for PDCP PDUs, and transmit the PDCP PDUsto the PDCP layer, which performs decryption, integrity de-protection,header decompression, etc., thereon in advance.

Upon reception of the PDCP PDUs transmitted from the RLC layer, the PDCPlayer determines whether they are normal data packets in the receptionwindow, whether they are duplicate, etc., performs de-encryption,integrity de-protection, header decompression, and other operations onpackets satisfying the reception condition, and thereafter reorders thedata packets, and if they satisfy a delivery-in-order requirement, thenthe PDCP layer may deliver them to the higher layer; otherwise, the PDCPlayer will wait to reorder them, and deliver all of them to the higherlayer in order after data at a gap are subsequently supplemented.

II. Implementations in which two modules among the receiving module, thetransmitting module, and the parsing module are located in the sameentity or different entities, or the receiving module, the transmittingmodule, and the parsing module are connected over a non-ideal backhaulwill be described below.

FIG. 4B illustrates typical processing of uplink data in a CU/DU entity.

Here, for example, the parsing module is located in a CU, and thetransmitting module and the receiving module are located in a DU.

1. Upon reception of MAC PDU data, the MAC layer (i.e., the receivingmodule) in the DU parses the data for RLC PDUs or RLC PDU segments ofdifferent logical channels, and transmits them to an RLC lower module(i.e., the transmitting module) in the DU.

2. The RLC Lower module may not process them, but deliver them directlyto an RLC Higher module (i.e., the parsing module) in the CU, or the RLCLower module may reorder and recombine, and then deliver them to the RLCHigher module.

3. The RLC Higher module performs reordering and necessaryrecombination, and other operations on the RLC PDUs or the RLC PDUsegments, and feeds backs a state report as specified; and the RLCHigher module transmits PDCP PDUs obtained as a result of parsing to thePDCP layer.

4. The PDCP layer performs decryption, integrity de-protection, headerdecompression, and other operations thereon, and then reorders them inthe AM mode, and delivers them to a higher layer in order.

As can be apparent from the description above, in the embodiment of theapplication, the respective layers can further process processed layer-2data of each other to thereby improve the real-time efficiency ofprocessing, and there are a uniform format and processing flow ofinitially transmitted and retransmitted segments to thereby lower thecomplexity of processing, and improve the efficiency of layer-2processing of a large number of data packets so as to be more applicableto various future 5G application scenarios.

Based upon the same inventive idea, an embodiment of the applicationfurther provides a system for transmitting data, and since the systemaddresses the problem under a similar principle to the method fortransmitting data according to the embodiment of the application,reference can be made to the implementation of the method for animplementation of the system, and a repeated description thereof will beomitted here.

As illustrated in FIG. 6, a system for transmitting data according to anembodiment of the application includes: an allocating module 600 isconfigured to compose RLC PDUs from received PDCP PDUs, and to allocatecorresponding RLC SNs for the composed RLC PDUs, where each RLC PDUcorresponds to one RLC SN, and each RLC PDU includes at least one PDCPPDU; a determining module 601 is configured to determine datacorresponding to a scheduled resource from the composed RLC PDUsaccording to the size of the scheduled resource; and a processing module602 is configured to compose MAC PDUs from the data corresponding to thescheduled resource, and to transmit the MAC PDUs.

Optionally the allocating module 600 is configured: to allocatecorresponding RLC SNs in the order in which respective PDCP PDUs at thesame priority are received.

Optionally the allocating module 600 is configured: to allocate RLC SNspreferentially for RLC PDUs composed from PDCP PDUs at a high priority.

Optionally each composed RLC PDU includes at least one of the receivedPDCP PDUs, and an RLC SN allocated for the composed RLC PDU; or if theorder of PDCP SNs of the respective received PDCP PDUs is the same asthe order of the allocated RLC SNs for the composed RLC PDUs, then eachcomposed RLC PDU will include at least one of the received PDCP PDUs.

Optionally the allocating module 600 is configured: to compose thecomposed RLC PDUs from the received PDCP PDUs before the size of thescheduled resource is determined; or to compose the composed RLC PDUsfrom the received PDCP PDUs after the size of the scheduled resource isdetermined.

Optionally the determining module 601 is configured: if it is determinedaccording to the size of the scheduled resource that segmentation is tobe performed, to determine a target RLC PDU to be segmented, accordingto the size of the scheduled resource, and to segment the target RLC PDUto generate a new RLC PDU.

Optionally the determining module 601 is configured: to generate the newRLC PDU according to segmentation information and data segmented fromthe target RLC PDU; where the segmentation information includes a partor all of the following information: an RLC SN of the target RLC PDU;start positional information of the data segmented from the target RLCPDU in the target RLC PDU; length information of the data segmented fromthe target RLC PDU; or an indicator indicating whether the datasegmented from the target RLC PDU is the last data segment in the targetRLC PDU.

Optionally the processing module 602 is configured: to order RLC PDUs ofthe same logical channel according to their RLC SNs, and to order RLCPDUs of different logical channels according to their priorities; and tocompose the MAC PDUs from the ordered RLC PDUs.

Optionally the processing module 602 is configured: to compose the MACPPDUs according to the LCIDs of the ordered RLC PDUs; where a MAC PDUcomprises LCIDs of the respective RLC PDUs comprised in the MAC PDU; ora MAC PDU comprises different LCIDs, and there is a common LCID for RLCPDUs corresponding to the same LCID.

Optionally each RLC PDU is an initially transmitted RLC PDUs, and/or aretransmitted RLC PDU.

Optionally the allocating module 600, the determining module 601, andthe processing module 602 are located in the same entity; or two modulesamong the allocating module 600, the determining module 601, and theprocessing module 602 are located in the same entity; or the allocatingmodule 600, the determining module 601, and the processing module 602are located in different entities.

Optionally if the allocating module 600, the determining module 601, andthe processing module 602 are located in the same entity, then theentity will be an eNB or a UE or a DU; or if two modules among theallocating module 600, the determining module 601, and the processingmodule 602 are located in the same entity, then the allocating module600 will be located in a CU, and the determining module 601 and theprocessing module 602 will be located in a DU.

Based upon the same inventive idea, an embodiment of the applicationfurther provides a system for receiving data, and since the systemaddresses the problem under a similar principle to the method forreceiving data according to the embodiment of the application, referencecan be made to the implementation of the method for an implementation ofthe system, and a repeated description thereof will be omitted here.

As illustrated in FIG. 7, a system for receiving data according to anembodiment of the application includes: a receiving module 700 isconfigured to separate a received MAC PDU into a plurality of RLC PDUs;a transmitting module 701 is configured to transmit received RLC PDUs toa parsing module; and the parsing module 702 is configured to parseordered and/or recombined RLC PDUs for PDCP PDUs upon determining thatthe RLC PDUs can be parsed, where each RLC PDU corresponds to one RLCSN, and each RLC PDU includes at least one PDCP PDU.

Optionally the parsing module 702 is further configured: to generatefeedback information according to RLC SNs of the received RLC PDUs;where if there is a lost RLC PDU which is not segmented, then thefeedback information will include the RLC SN of the lost RLC PDU; or ifthere is a lost RLC PDU segment, then the feedback information willinclude an RLC SN of the original RLC PDU including the lost RLC PDUsegment, information indicating the start position of the lost RLC PDUsegment in the original RLC PDU, and length information of the lost RLCPDU segment; or if there are consecutive RLC PDUs which are lost, andthere is no segmented RLC PDU among the consecutive RLC PDUs, then thefeedback information will include the RLC SN of the first RLC PDU amongthe consecutive RLC PDUs, and the number of lost RLC PDUs; or if thereare consecutive RLC PDUs which are lost, and there is a segmented RLCPDU among the consecutive RLC PDUs, then the feedback information willinclude the RLC SN of the first RLC PDU among the consecutive RLC PDUs,information indicating the segmented RLC PDU, and the number of lost RLCPDUs, where the segmented RLC PDU is the first RLC PDU and/or the lastRLC PDU among the consecutive RLC PDUs.

Optionally the transmitting module 701 is configured: to transmit thereceived RLC PDUs directly to the parsing module; or to order and/orrecombine the received RLC PDUs according to RLC SNs of the received RLCPDUs, and then transmit the ordered and/or recombined RLC PDUs to theparsing module.

Optionally the receiving module 700, the transmitting module 701, andthe parsing module 702 are located in the same entity; or two modulesamong the receiving module 700, the transmitting module 701, and theparsing module 702 are located in the same entity; or the receivingmodule 700, the transmitting module 701, and the parsing module 702 arelocated in different entities.

Optionally if the receiving module 700, the transmitting module 701, andthe parsing module 702 are located in the same entity, then the entitywill be an eNB or a UE or a DU; or if two modules among the receivingmodule 700, the transmitting module 701, and the parsing module 702 arelocated in the same entity, then the parsing module 702 will be locatedin a CU, and the receiving module 700 and the transmitting module 701will be located in a DU.

FIG. 8 illustrates an example in which the allocating module 600, thedetermining module 601, and the processing module 602 are located in thesame entity, and structures in which two modules among the allocatingmodule 600, the determining module 601, and the processing module 602are located in the same entity or different entities will be similar tothe structure as illustrated in FIG. 8 except that a processor performsthe function or functions of one or more of the modules, so a repeateddescription thereof will be omitted here.

Based upon the same idea, an embodiment of the application furtherprovides a transmitting device, and since the device addresses theproblem under a similar principle to the method for transmitting dataaccording to the embodiment of the application, reference can be made tothe implementation of the method for an implementation of the device,and a repeated description thereof will be omitted here.

As illustrated in FIG. 8, a transmitting device according to anembodiment of the application includes: a processor 801 is configured toread and execute program in a memory 804: to compose RLC PDUs fromreceived PDCP PDUs, and to allocate corresponding RLC SNs for thecomposed RLC PDUs, where each RLC PDU corresponds to one RLC SN, andeach RLC PDU includes at least one PDCP PDU; to determine datacorresponding to a scheduled resource from the composed RLC PDUsaccording to the size of the scheduled resource; and to compose MAC PDUsfrom the data corresponding to the scheduled resource, and to transmitthe MAC PDUs.

A transceiver 802 is configured to receive and transmit data under thecontrol of the processor 801.

Optionally the processor 801 is configured: to allocate correspondingRLC SNs in the order in which respective PDCP PDUs at the same priorityare received.

Optionally the processor 801 is configured: to allocate RLC SNspreferentially for RLC PDUs composed from PDCP PDUs at a high priority.

Optionally each composed RLC PDU includes at least one of the receivedPDCP PDUs, and an RLC SN allocated for the composed RLC PDU; or if theorder of PDCP SNs of the respective received PDCP PDUs is the same asthe order of the allocated RLC SNs for the composed RLC PDUs, then eachcomposed RLC PDU will include at least one of the received PDCP PDUs.

Optionally the processor 801 is configured: to compose the composed RLCPDUs from the received PDCP PDUs before the size of the scheduledresource is determined; or to compose the composed RLC PDUs from thereceived PDCP PDUs after the size of the scheduled resource isdetermined.

Optionally the processor 801 is configured: if it is determinedaccording to the size of the scheduled resource that segmentation is tobe performed, to determine a target RLC PDU to be segmented, accordingto the size of the scheduled resource, and to segment the target RLC PDUto generate a new RLC PDU.

Optionally the processor 801 is configured: to generate the new RLC PDUaccording to segmentation information and data segmented from the targetRLC PDU; where the segmentation information includes a part or all ofthe following information: an RLC SN of the target RLC PDU; startpositional information of the data segmented from the target RLC PDU inthe target RLC PDU; length information of the data segmented from thetarget RLC PDU; or an indicator indicating whether the data segmentedfrom the target RLC PDU is the last data segment in the target RLC PDU.

Optionally the processor 801 is configured: to order RLC PDUs of thesame logical channel according to their RLC SNs, and to order RLC PDUsof different logical channels according to their priorities; and tocompose the MAC PDUs from the ordered RLC PDUs.

Optionally the processor 801 is configured: to compose the MACP PDUsaccording to the LCIDs of the ordered RLC PDUs; where a MAC PDUcomprises LCIDs of the respective RLC PDUs comprised in the MAC PDU; ora MAC PDU comprises different LCIDs, and there is a common LCID for RLCPDUs corresponding to the same LCID.

Optionally each RLC PDU is an initially transmitted RLC PDUs, and/or aretransmitted RLC PDU.

In FIG. 8, the bus architecture (represented by the bus 800) can includeany number of interconnecting buses and bridges to particularly linktogether various circuits including one or more processors representedby the processor 801, and one or more memories represented by the memory804. The bus 800 can further link together various other circuits, e.g.,a peripheral device, a manostat, a power management circuit, etc., allof which are well known in the art, so a further description thereofwill be omitted in this context. The bus interface 803 serves aninterface between the bus 800 and the transceiver 802. The transceiver802 can be an element, or a number of elements, e.g., a number oftransmitters and receivers, which are units for communication withvarious other devices over a transmission medium. Data processed by theprocessor 801 are transmitted over a radio medium through the antenna805, and furthermore the antenna 805 receives data and transmits thedata to the processor 801.

The processor 801 is responsible for managing the bus 800 and performingnormal processes, and can further various functions including timing, aperipheral interface, voltage regulation, power source management, andother control functions, and the memory 804 can store data for use bythe processor 801 in performing the operations.

Optionally the processor 801 can be a Central Processing Unit (CPU), anApplication-Specific Integrated Circuit (ASIC), a Field-ProgrammableGate Array (FPGA), or a Complex Programmable Logic Device (CPLD).

Based upon the same inventive idea, an embodiment of the applicationfurther provides a receiving device, and since the device addresses theproblem under a similar principle to the method for receiving dataaccording to the embodiment of the application, reference can be made tothe implementation of the method for an implementation of the device,and a repeated description thereof will be omitted here.

FIG. 9 illustrates an example in which the receiving module 700, thetransmitting module 701, and the parsing module 702 are located in thesame entity, and structures in which two modules among the receivingmodule 700, the transmitting module 701, and the parsing module 702 arelocated in the same entity or different entities will be similar to thestructure as illustrated in FIG. 9 except that a processor performs thefunction or functions of one or more of the modules, so a repeateddescription thereof will be omitted here.

As illustrated in FIG. 9, a receiving device according to an embodimentof the application includes: a processor 901 is configured to read andexecute program in a memory 904: to separate a received MAC PDU into aplurality of RLC PDUs; to transmit received RLC PDUs to a parsingmodule; and to parse ordered and/or recombined RLC PDUs for PDCP PDUsupon determining that the RLC PDUs can be parsed, where each RLC PDUcorresponds to one RLC SN, and each RLC PDU includes at least one PDCPPDU.

A transceiver 902 is configured to receive and transmit data under thecontrol of the processor 901.

Optionally the processor 901 is further configured: to generate feedbackinformation according to RLC SNs of the received RLC PDUs; where ifthere is a lost RLC PDU which is not segmented, then the feedbackinformation will include the RLC SN of the lost RLC PDU; or if there isa lost RLC PDU segment, then the feedback information will include theRLC SN of the original RLC PDU including the lost RLC PDU segment,information indicating the start position of the lost RLC PDU segment inthe original RLC PDU, and length information of the lost RLC PDUsegment; or if there are consecutive RLC PDUs which are lost, and thereis no segmented RLC PDU among the consecutive RLC PDUs, then thefeedback information will include the RLC SN of the first RLC PDU amongthe consecutive RLC PDUs, and the number of lost RLC PDUs; or if thereare consecutive RLC PDUs which are lost, and there is a segmented RLCPDU among the consecutive RLC PDUs, then the feedback information willinclude the RLC SN of the first RLC PDU among the consecutive RLC PDUs,information indicating the segmented RLC PDU, and the number of lost RLCPDUs, where the segmented RLC PDU is the first RLC PDU and/or the lastRLC PDU among the consecutive RLC PDUs.

Optionally the processor 901 is configured: to transmit the received RLCPDUs directly to the parsing module; or to order and/or recombine thereceived RLC PDUs according to the RLC SNs of the received RLC PDUs, andthen transmit the ordered and/or recombined RLC PDUs to the parsingmodule.

In FIG. 9, the bus architecture (represented by the bus 900) can includeany number of interconnecting buses and bridges to particularly linktogether various circuits including one or more processors representedby the processor 901, and one or more memories represented by the memory904. The bus 900 can further link together various other circuits, e.g.,a peripheral device, a manostat, a power management circuit, etc., allof which are well known in the art, so a further description thereofwill be omitted in this context. The bus interface 903 serves aninterface between the bus 900 and the transceiver 902. The transceiver902 can be an element, or a number of elements, e.g., a number oftransmitters and receivers, which are units for communication withvarious other devices over a transmission medium. Data processed by theprocessor 901 are transmitted over a radio medium through the antenna905, and furthermore the antenna 905 receives data and transmits thedata to the processor 901.

The processor 901 is responsible for managing the bus 900 and performingnormal processes, and can further various functions including timing, aperipheral interface, voltage regulation, power source management, andother control functions, and the memory 904 can store data for use bythe processor 901 in performing the operations.

Optionally the processor 901 can be a CPU, an ASIC, an FPGA, or a CPLD.

The application has been described in a flow chart and/or a blockdiagram of the method, the device (system) and the computer programproduct according to the embodiments of the application. It shall beappreciated that respective flows and/or blocks in the flow chart and/orthe block diagram and combinations of the flows and/or the blocks in theflow chart and/or the block diagram can be embodied in computer programinstructions. These computer program instructions can be loaded onto ageneral-purpose computer, a specific-purpose computer, an embeddedprocessor or a processor of another programmable data processing deviceto produce a machine so that the instructions executed on the computeror the processor of the other programmable data processing device createmeans for performing the functions specified in the flow(s) of the flowchart and/or the block(s) of the block diagram.

Correspondingly the application can be further embodied in hardwareand/or software (including firmware, resident software, micro-codes,etc.). Still furthermore the application can be embodied in the form ofa computer program product on a computer useable or readable storagemedium, where the computer program product includes computer useable orreadable program codes embodied in the medium to be used by or inconnection with an instruction executing system. In the context of theapplication, the computer useable or readable medium can be any mediumwhich can include, store, communicate, transmit, or transport program tobe used by or in connection with an instruction executing system,apparatus or device.

Evidently those skilled in the art can make various modifications andvariations to the application without departing from the spirit andscope of the application. Thus the application is also intended toencompass these modifications and variations thereto so long as themodifications and variations come into the scope of the claims appendedto the application and their equivalents.

The invention claimed is:
 1. A method for transmitting data, the methodcomprising: composing Radio Link Control Protocol Data Units (RLC PDUs)from received Packet Data Convergence Protocol Data Units (PDCP PDUs),and allocating corresponding Radio Link Control Sequence Numbers (RLCSNs) for the composed RLC PDUs, wherein each RLC PDU corresponds to oneRLC SN, and each RLC PDU comprises at least one PDCP PDU; determiningdata corresponding to a scheduled resource from the composed RLC PDUsaccording to the size of the scheduled resource; and composing MediaAccess Control Protocol Data Units (MAC PDUs) from the datacorresponding to the scheduled resource, and transmitting the MAC PDUs;wherein the allocating the corresponding RLC SNs for the composed RLCPDUs, comprises: allocating RLC SNs preferentially for RLC PDUs composedfrom PDCP PDUs at a high priority, and allocating corresponding RLC SNsin the order in which respective PDCP PDUs at the same priority arereceived; or allocating RLC SNs preferentially for RLC PDUs composedfrom PDCP PDUs at a high priority, and allocating corresponding RLC SNsin the order in which respective sets of PDCP PDUs at the same priorityare received, wherein each set of PDCP PDUs comprises at least one PDCPPDU.
 2. The method according to claim 1, wherein each composed RLC PDUcomprises at least one of the received PDCP PDUs, and an RLC SNallocated for the composed RLC PDU; or if the order of Packet DataConvergence Protocol Sequence Numbers (PDCP SNs) of the respectivereceived PDCP PDUs is the same as the order of the allocated RLC SNs forthe composed RLC PDUs, then each composed RLC PDU comprises at least oneof the received PDCP PDUs.
 3. The method according to claim 1, whereinthe composing the composed RLC PDUs from the received PDCP PDUscomprises: composing the composed RLC PDUs from the received PDCP PDUsbefore the size of the scheduled resource is determined; or composingthe composed RLC PDUs from the received PDCP PDUs after the size of thescheduled resource is determined.
 4. The method according to claim 1,wherein the determining the data corresponding to the scheduled resourcefrom the composed RLC PDUs according to the size of the scheduledresource comprises: if segmentation is determined, according to the sizeof the scheduled resource, to be performed, then determining a targetRLC PDU to be segmented, according to the size of the scheduledresource, and segmenting the target RLC PDU to generate a new RLC PDU;wherein the segmenting the target RLC PDU to generate the new RLC PDUcomprises: generating the new RLC PDU according to segmentationinformation and data segmented from the target RLC PDU; wherein thesegmentation information comprises a part or all of the followinginformation: an RLC SN of the target RLC PDU; start positionalinformation of the data segmented from the target RLC PDU in the targetRLC PDU; length information of the data segmented from the target RLCPDU; or an indicator indicating whether the data segmented from thetarget RLC PDU is the last data segment in the target RLC PDU.
 5. Themethod according to claim 1, wherein the composing the MAC PDUs from thedata corresponding to the scheduled data comprises: ordering RLC PDUs ofthe same logical channel according to their RLC SNs, and ordering RLCPDUs of different logical channels according to their priorities; andcomposing the MAC PDUs from the ordered RLC PDUs; wherein composing theMAC PDUs from the ordered RLC PDUs comprises: composing the MACP PDUsaccording to Logical Channel IDs (LCIDs) of the ordered RLC PDUs;wherein a MAC PDU comprises LCIDs of respective RLC PDUs comprised inthe MAC PDU; or a MAC PDU comprises different LCIDs, and there is acommon LCID for RLC PDUs corresponding to the same LCD.
 6. The methodaccording to claim 1, wherein each RLC PDU is an initially transmittedRLC PDU, or a retransmitted RLC PDU.
 7. A transmitting device,comprising: a processor configured to read and execute program in amemory: to compose Radio Link Control Protocol Data Units (RLC PDUs)from received Packet Data Convergence Protocol Data Units (PDCP PDUs),and to allocate corresponding Radio Link Control Sequence Numbers (RLCSNs) for the composed RLC PDUs, wherein each RLC PDU corresponds to oneRLC SN, and each RLC PDU comprises at least one PDCP PDU; to determinedata corresponding to a scheduled resource from the composed RLC PDUsaccording to the size of the scheduled resource; and to compose MediaAccess Control Protocol Data Units (MAC PDUs) from the datacorresponding to the scheduled resource, and to transmit the MAC PDUs; atransceiver configured to receive and transmit data under the control ofthe processor; wherein the processor is configured to: allocate RLC SNspreferentially for RLC PDUs composed from PDCP PDUs at a high priority,and allocate corresponding RLC SNs in the order in which respective PDCPPDUs at the same priority are received; or allocate RLC SNspreferentially for RLC PDUs composed from PDCP PDUs at a high priority,and allocate corresponding RLC SNs in the order in which respective setsof PDCP PDUs at the same priority are received, wherein each set of PDCPPDUs comprises at least one PDCP PDU.
 8. The device according to claim7, wherein each composed RLC PDU comprises at least one of the receivedPDCP PDUs, and an RLC SN allocated for the composed RLC PDU; or if theorder of Packet Data Convergence Protocol Sequence Numbers (PDCP SNs) ofthe respective received PDCP PDUs is the same as the order of theallocated RLC SNs for the composed RLC PDUs, then each composed RLC PDUcomprises at least one of the received PDCP PDUs.
 9. The deviceaccording to claim 7, wherein if the processor determines according tothe size of the scheduled resource that segmentation is to be performed,then the processor is configured to determine a target RLC PDU to besegmented, according to the size of the scheduled resource, and segmentthe target RLC PDU to generate a new RLC PDU; wherein the processor isfurther configured to generate the new RLC PDU according to segmentationinformation and data segmented from the target RLC PDU; wherein thesegmentation information comprises a part or all of the followinginformation: an RLC SN of the target RLC PDU; start positionalinformation of the data segmented from the target RLC PDU in the targetRLC PDU; length information of the data segmented from the target RLCPDU; or an indicator indicating whether the data segmented from thetarget RLC PDU is the last data segment in the target RLC PDU.
 10. Thedevice according to claim 7, wherein the processor is configured toorder RLC PDUs of the same logical channel according to their RLC SNs,and order RLC PDUs of different logical channels according to theirpriorities; and compose the MAC PDUs from the ordered RLC PDUs; whereinthe processor is further configured to: compose the MACP PDUs accordingto Logical Channel IDs (LCIDs) of the ordered RLC PDUs; wherein a MACPDU comprises LCIDs of respective RLC PDUs comprised in the MAC PDU; ora MAC PDU comprises different LCIDs, and there is a common LCID for RLCPDUs corresponding to the same LCD.
 11. The device according to claim 7,wherein each RLC PDU is an initially transmitted RLC PDU, or aretransmitted RLC PDU.